CVE-2026-2053
Unauthenticated Server-Side Request Forgery via WS-Addressing in WSO2 API Manager
Description
The WSO2 API Manager's message flow component, when processing WS-Addressing headers, does not sufficiently validate or restrict user-controlled input within these headers. This omission allows an attacker to manipulate WS-Addressing headers to specify arbitrary destinations for server-initiated requests. Successful exploitation allows an unauthenticated attacker to control the destination of server-initiated requests originating from the WSO2 API Manager. This direct control can enable unauthorized access to internal network resources or services that would typically be inaccessible from external networks.
INFO
Published Date :
June 26, 2026, 7:26 a.m.
Last Modified :
June 26, 2026, 7:26 a.m.
Remotely Exploit :
Yes !
Source :
WSO2
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | ed10eef1-636d-4fbe-9993-6890dfa878f8 |
Solution
- Validate WS-Addressing headers for user-controlled input.
- Restrict destinations for server-initiated requests.
- Apply vendor patches or updates for WSO2 API Manager.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-2053 vulnerability anywhere in the article.